Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊
| Attribute | Value |
|---|---|
| Connector ID | RedRaysSAPSecurityFindings |
| Publisher | RedRays, Inc. |
| Used in Solutions | RedRays SAP Security Findings |
| Collection Method | CCF Push |
| Connector Definition Files | RedRaysSAPSecurityFindings_connectorDefinition.json |
| DCR Definition Files | RedRaysSAPSecurityFindings_DCR.json |
| CCF Configuration | RedRaysSAPSecurityFindings_PollerConfig.json |
| CCF Capabilities | Push |
| Ingestion API | Log Ingestion API — CCF Push connectors use DCR-based Log Ingestion API |
Bring RedRays SAP security findings into Microsoft Sentinel. Review vulnerability assessments, ABAP code findings, BTP security, segregation of duties, profile parameter checks and password security in one workbook, with analytics rules for findings that need attention. RedRays pushes data on a schedule you choose through the Azure Monitor Logs Ingestion API and stays in your existing on-premises or cloud environment. This connector does not collect SAP Security Audit Log events or populate ABAPAuditLog. You need a RedRays license with Microsoft Sentinel integration. Azure ingestion and retention charges apply.
This connector ingests data into the following tables:
| Table | Transformations | Ingestion API | Lake-Only |
|---|---|---|---|
RedRaysAbapFindings_CL |
? | ✓ | ? |
RedRaysCloudFindings_CL |
? | ✓ | ? |
RedRaysExportHealth_CL |
? | ✓ | ? |
RedRaysPasswordFindings_CL |
? | ✓ | ? |
RedRaysProfileChecks_CL |
? | ✓ | ? |
RedRaysScanRuns_CL |
? | ✓ | ? |
RedRaysSoDFindings_CL |
? | ✓ | ? |
RedRaysVulnerabilities_CL |
? | ✓ | ? |
💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.
Resource Provider Permissions:
Custom Permissions:
⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.
1. Deploy the push connector resources
Select Deploy to create a data collection endpoint (DCE), a data collection rule (DCR) and the eight RedRays tables in this workspace. Microsoft Sentinel also creates a Microsoft Entra app registration with a client secret and grants it the Monitoring Metrics Publisher role on the DCR, so RedRays can send data with OAuth 2.0 client credentials. Workspace shared keys are not used.
ℹ️ The client secret is shown only once, right after deployment. Copy it immediately. If you miss it, open Microsoft Entra ID > App registrations, select RedRays SAP Security Findings, and create a new client secret under Certificates & secrets. Deploy
2. Configure RedRays
In RedRays, open Platform Settings > Microsoft Sentinel and enter the values below. Choose the modules to export and how often to send data. Keep baseline alerting disabled for the first import, then save and enable the integration. RedRays needs outbound HTTPS access to Microsoft Entra and the data collection endpoint. No inbound connection is required.
TenantIdNote: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.
ApplicationIdNote: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.
ApplicationSecretNote: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.
DataCollectionEndpointNote: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.
DataCollectionRuleIdNote: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.
3. Verify delivery
Send a test event from RedRays, then wait for a scheduled export. Query RedRaysExportHealth_CL for RecordKind == 'HEARTBEAT'. A successful test means Azure accepted the request; the record may take a few minutes to appear in queries. RedRays sends each module to its own stream (Custom-RedRaysExportHealth_CL, Custom-RedRaysScanRuns_CL, Custom-RedRaysVulnerabilities_CL, Custom-RedRaysAbapFindings_CL, Custom-RedRaysCloudFindings_CL, Custom-RedRaysSoDFindings_CL, Custom-RedRaysProfileChecks_CL and Custom-RedRaysPasswordFindings_CL) on the same DCR.
4. Enable security content
Open Manage solution to create the workbook and selected analytics rules from templates. Review the initial findings before enabling rules. Most finding rules alert on actionable High or Critical candidates. The profile rule raises Medium severity alerts for VULNERABLE checks. The workbook flags heartbeats older than 60 minutes; adjust the threshold above your export interval and expected ingestion delay. Disable equivalent rules from earlier RedRays deployments to avoid duplicate alerts. For help, contact support@redrays.io.
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊